TELECOMMUNICATION SYSTEM COMPRISING AN O&amp;M (Operation and Maintenance) HIERARCHICAL LAYER STRUCTURE

ABSTRACT

A telecommunication system comprising an O&amp;M (Operation and Maintenance) hierarchical layer structure comprising at least two O&amp;M nodes in at least two hierarchical layers, where O&amp;M actions may be initiated at said nodes. The system is arranged for generation of an O&amp;M transaction identifier when an O&amp;M action is initiated, and is transferred to all nodes in all management layers used for said O&amp;M action, which is initiated inside an O&amp;M session, allowing O&amp;M actions and sessions to be tracked in the O&amp;M hierarchical layer structure. The present invention also relates to a method for tracking O&amp;M actions in an O&amp;M hierarchical layer structure.

TECHNICAL FIELD

The present invention relates to a telecommunication system comprisingan O&M (Operation and Maintenance) hierarchical layer structurecomprising at least two O&M nodes in at least two hierarchical layers,where O&M actions may be initiated at said nodes.

The present invention also relates to a method for tracking O&M(Operation and Maintenance) actions in an O&M hierarchical layerstructure.

BACKGROUND

In a modern telecommunication system, for example a 3GPP based mobiletelecommunication system such as WCDMA (Wide Code Division MutlipleAccess), there is usually a management system, which normally has anarchitecture where the management system is divided into a number ofseparate layers. In these layers, O&M (Operation and Maintenance) isperformed. O&M management functions generally cover all tasks andfunctions performed by a network operator for administering andmonitoring their network, for example network elements, routers andswitches. Examples of these functions are activities related to faultmanagement, performance management, configuration management etc.

As O&M systems are getting more complex, being able to serve larger andlarger networks, it is very important that all user activities arelogged properly, since it is necessary to keep track of who did what andwhen across all nodes. This kind of information is needed in order to beable to ensure that relevant information regarding the performed O&Mactions are available, to be used for example when analysing faultsituations afterwards.

When there are O&M management systems in different layers, havingdifferent O&M applications running in these layers, many applicationsproduce their own log files for accountability purposes. Then, itbecomes very difficult to correlate the information related to thosetasks which are performed by an O&M user within one O&M session. Thiskind of correlation is needed, and in some cases even required bynetwork operators, in order to be able to trace individual useractivities throughout a complete O&M system.

Today, the correlation is mainly done by analysing a number ofparameters, for example user id's, and time stamps which are availablein corresponding logs. In some cases it will even be impossible toperform a correlation at all, since the user id's in those cases are nottransferred from one layer or application to another.

There is thus a need for a system, and a method, for easy tracing andcorrelation of O&M user activities, because vital information such asuser id, time stamps for performed O&M actions is very often missingfrom the logs.

SUMMARY

The aim of the present invention to disclose a system, and a method, foreasy tracing and correlation of O&M user activities.

This aim is achieved by means of a telecommunication system according tothe introduction, where furthermore the system is arranged forgeneration of an O&M transaction identifier, which O&M transactionidentifier is generated when an O&M action is initiated, and istransferred to all nodes in all management layers used for said O&Maction, said O&M action being initiated inside an O&M session, allowingO&M actions and sessions to be tracked in the O&M hierarchical layerstructure.

In a preferred embodiment, the hierarchical layers comprise a networkmanagement layer, a sub network management layer and an elementmanagement layer, the layers forming an O&M hierarchical layerstructure.

In another preferred embodiment, any node where an O&M action isinitiated, is arranged to generate an O&M transaction identifier and,when needed, to transfer the O&M transaction identifier.

In another preferred embodiment, each O&M transaction identifiercomprises an O&M session identifier and an O&M action identifier, theO&M session identifier being generated when an O&M session is initiated,and the O&M action identifier being generated when an O&M action isinitiated inside an O&M session, the O&M transaction identifier thusbeing generated when an O&M action is initiated.

In another preferred embodiment, the O&M transaction identifier consistsof a node identification part comprising an IP-address, or a FullyQualified Domain Name, an O&M session identification part comprising arunning sequence number and an O&M action identification part comprisinga O&M session specific running number.

Other preferred embodiments are disclosed in the dependent claims.

This aim is also achieved by means of a method according to theintroduction, where further said method comprises the following stepswhen an O&M action is performed at a node in the O&M hierarchical layerstructure, said O&M action being initiated inside an O&M session:generating an O&M transaction identifier; distributing the action in theform of a command to at least one other node in the O&M hierarchicallayer structure; making the original O&M transaction identifieravailable as a corresponding O&M transaction identifier at said othernode, the original O&M transaction identifier thus being available inall nodes, making it possible to trace the O&M activity throughout theO&M hierarchical layer structure.

In a preferred embodiment, an O&M transaction identifier is generated atany node where an O&M action is initiated and, when needed, said nodetransfers said O&M transaction identifier.

Other preferred embodiments are disclosed in the dependent claims.

Several advantages are achieved by means of the present invention, forexample:

-   -   easy tracing and correlation of O&M user activities; and    -   securing vital information such as user id, time stamps for        performed O&M actions etc.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be described more in detail withreference to the appended drawings, where

FIG. 1 schematically shows a management system architecture in atelecommunication network system;

FIG. 2 schematically shows a node with an O&M transaction identifieraccording to the present invention; and

FIG. 3 schematically shows an O&M action being initiated from an NMS andbeing “deployed” to an SNM and related network elements.

DETAILED DESCRIPTION

In FIG. 1, a management system architecture 1 intended for use in a 3G(third generation) telecommunication network system 2 is shown, saidmanagement system architecture 1 being divided into a number of 5hierarchical layers. In FIG. 1, a top layer 3, a middle layer 4 and abottom layer 5 is shown. The top layer 3 is a network management layer,the middle layer 4 is a sub network management layer and the bottomlayer 5 is an element management layer. The layers 3, 4, 5 form an O&Mhierarchical layer structure 6.

The network management layer 3 at least comprises a node of the type NMS(Network Management System) 7 which in turn comprises applications forspecific aspects of all parts of the complete network system 2, forexample fault handling. In this layer 3, management of the completenetwork system 2 is carried out. The network system 2 may additionallycomprise several systems, for example both a 2G (second generation) anda 3G system.

The sub network management layer 4 at least comprises a node of the typeSNM (Sub-network Management System) 8, which is arranged to supportcentralized O&M for a part of the complete network system, for examplefor a radio access network. The SNM 8 contains management applicationsfor day-to-day handling of O&M functions, such as collection andevaluation of alarms and performance data.

Different SNM:s may be comprised in the sub network management layer 4,for example a first SNM 9 for a service layer (entities providingservices to end-users and content & application providers), a second SNM10 for IP Multimedia Systems (network architecture standardized by ETSI(European Telecommunications Standards Institute) for operators toprovide IP based mobile and fixed multimedia services), a third SNM 11for a core network (entities providing circuit-switched and packetswitched services) and a fourth SNM 12 for a radio network (entitiesproviding a radio access for wireless systems).

The NMS 7 and SNM 8 usually support open interfaces, such as 3GPP (₃rdGeneration Partnership Project) IRP (Integration Reference Point) basedon for example CORBA (Common Object Request Broker Architecture). Theelement management layer 5 manages individual nodes 13, 14, 15, 16, suchas an RNC (Radio Network Controller), an SGSN (Switching GPRS SupportNode), CSCF (Call Session Control Function) and various other networkequipment such as routers and switches. The nodes are usually interfacedby means of corresponding node element managers 17, 18, 19, 20. A nodeelement manager is an entity (typically a Windows or Unix client basedGUI (General User Interface)) used to administer a node that encompassesO&M management functions.

According to the present invention, with reference to FIG. 2, when anO&M user initiates an O&M session, an O&M session identifier isgenerated. When an O&M action is initiated inside an O&M session, an O&Maction identifier 20 is generated in the node 21, for example NMS orSNM. Together with a node identification, the O&M session identifier andthe O&M action identifier constitute an O&M transaction identifier. Forinstance, the node identification can be a configurable string, such as“OSS-STOCKHOLM, “MSC33” or “GGSN_TELIASONERA”.

A user is preferably authenticated before an O&M transaction identifieris generated. When a user initiates a new O&M action, a new O&M actionidentifier is generated. When a user is referred to in this description,network operator O&M personnel or the like is meant, not a subscriber orthe like.

The O&M transaction identifier is then transferred 23, 24 to all nodesin all management layers 3, 4, 5 used for said O&M action. The O&Mtransaction identifier 20 will be available in logs produced forperformed O&M actions in concerned nodes, making it very easy tocorrelate information regarding the performed O&M actions afterwards.

Thus, any node 21 that performs authentication for a user can alsogenerate an O&M transaction identifier 20. The O&M transactionidentifier 20 should then be transferred to concerned nodes over usedO&M interfaces, thus making it possible for other applications or nodesto use the O&M transaction identifier 20, preferably for loggingpurposes. This also makes it possible to correlate actions performed bya user even if no user identification information is transferred betweenapplications or nodes.

The management applications, or nodes 7, 8, 9, 10, 11, 12, 13, 14, 15,16, in all layers 3, 4, 5 are arranged to be able to generate an O&Mtransaction identifier 20, and all used O&M protocols and interfaces areadopted to transfer the O&M transaction identifier 20.

In a preferred embodiment of the present invention, the O&M transactionidentifier 20 consists of three parts: a node identification part 25comprising an IP-address or a Fully Qualified Domain Name, an O&Msession identification part 26 a comprising a running sequence numberand an O&M action identification part 26 b comprising a O&M sessionspecific running number.

The usage of an O&M transaction identifier will now be described more indetail with reference to FIG. 3.

FIG. 3 illustrates an example where an O&M transaction identifier 20 a-gis used for correlation of O&M transaction information. In the example,it is assumed that an O&M action 27 is performed at the NMS 7 in thenetwork management layer 3, inside an O&M session. The action 27 is inthe form of a user defining a value A for a parameter X to be set in allnodes. First, an O&M transaction identifier 20 a is generated,comprising a session identifier and an action identifier. The NMS then 7distributes the action 27 in the form of a command 28 a to the SNM 8 inthe sub network management layer 4. The SNM 8 then distributes thecommand 28 b, 28 c, 28 d to individual network element nodes 13, 14, 15.The original O&M transaction identifier 20 a is then transferred T1 tothe SNM 8 and becomes available as O&M transaction identifiers 20 b, 20c, 20 d at the SNM 8, one O&M transaction identifier 20 b, 20 c, 20 dfor each distribution of the command 28 b, 28 c, 28 d to the individualnetwork element nodes 13, 14, 15. Furthermore, the original O&Mtransaction identifier 20 a is transferred T2 to the individual networkelement nodes 13, 14, 15 and thus becomes available as O&M transactionidentifiers 20 e, 20 f, 20 g at the individual network element nodes 13,14, 15 which received the respective command 28 b, 28 c, 28 d.

The same O&M transaction identifier thus is available in all logs in allnodes 7, 8, 13, 14, 15 which makes it possible to trace an O&M activity27 throughout the O&M network 1.

In the example above, the O&M action 27 can of course also be initiatedfrom the SNM 8 instead. In general, an O&M action may be initiated inany node in the O&M hierarchical layer structure 6.

An example of an O&M action may be a configuration of network nodes suchas for example an RNC. These actions can be performed in the networkmanagement layer 3, the sub-network management layer 4and/or the elementmanagement layer 5. The O&M action may then result in producedaccountability information, for example in the form of logs in severalmanagement applications as a result of the action being executed.

In the example above, and generally, the O&M user is authenticated andauthorized prior to being allowed to perform O&M actions. When theauthentication has been performed, the O&M application node in questiongenerates an O&M transaction identifier. When the O&M transactionidentifier has been generated, it is transferred further in theprotocols, for example CORBA, and interfaces used, together withinformation for the performed O&M actions.

If needed, all applications processing said information for generatinglogs, or for other purposes, uses the provided O&M transactionidentifier.

Afterwards, when data is processed in various post-processing systemsfor accountability purposes, it is possible to correlate and traceactivities performed by a certain user at a certain time.

The communication between the nodes in the example above takes placeusing so-called IRP:s (Integration Reference Point). IRP:s have beendeveloped to promote a wider adoption of standardized Managementinterfaces in telecommunication networks. The IRP methodology employsProtocol & Technology Neutral modelling methods as well as protocolspecific solution sets to help achieve its goals.

3GPP has standardized a number of IRP:s for O&M communication betweenmanagement systems and network elements. In the O&M architectureaccording to a preferred embodiment, IRP:s are used both for internaland external communication. This communication may be directed towardsother network operator's equipment. Thus, solutions provided for anyIRP:s may be adopted to certain specialized varieties.*

The present invention is not limited to the examples described above,but may be varied freely within the scope of the appended claims. Forexample, other layer configurations may be possible, the core of theinvention is to generate an O&M transaction identifier 20 in the node 21where an O&M action is initiated. The O&M transaction identifier 20 isthen transferred 23, 24 to all nodes in all management layers 3, 4, 5used for said O&M action.

The node 21 where an O&M action is initiated may be any node in an O&Mhierarchical layer structure 6.

The invention is applicable to all telecommunication systems that haveany type of O&M architecture, both wireless as well as wired.

The O&M transaction identifier 20 may consist of more or less then saidthree parts, examples of other parts is for example a date, time stampor operator specific information.

It is also possible that the O&M session identification part 26 a,comprising a running sequence number, and the O&M action identificationpart 26 b, comprising an O&M session specific running number, arecombined to one part, comprising only one running number.

1.-18. (canceled)
 19. A telecommunication system, comprising: anOperation and Maintenance (O&M) hierarchical layer structure comprisingat least two O&M nodes in at least two hierarchical layers, where O&Mactions may be initiated at said nodes, wherein the system is arrangedfor generation of an O&M transaction identifier, which O&M transactionidentifier is generated when an O&M action is initiated, and istransferred to all nodes in all management layers used for said O&Maction, said O&M action being initiated inside an O&M session, allowingO&M actions and sessions to be tracked in the O&M hierarchical layerstructure.
 20. The telecommunication system according to claim 19,wherein the hierarchical layers comprise a network management layer, asub network management layer and an element management layer, the layersforming an O&M hierarchical layer structure.
 21. The telecommunicationsystem according to claim 20, wherein the network management layer atleast comprises a node of the type Network Management System (NMS), thesub network management layer at least comprises a node of the typeSub-network Management System (SMS) and that the element managementlayer manages individual nodes which are interfaced by means ofcorresponding node element managers.
 22. The telecommunication systemaccording to claim 19 wherein, in any node where an O&M action isinitiated, said node is arranged to generate an O&M transactionidentifier and, when needed, to transfer the O&M transaction identifier.23. The telecommunication system according to claim 22, wherein said O&Mtransaction identifier is generated when the initiating user isauthenticated.
 24. The telecommunication system according to claim 19,wherein each O&M transaction identifier comprises an O&M sessionidentifier and an O&M action identifier, the O&M session identifierbeing generated when an O&M session is initiated, and the O&M actionidentifier being generated when an O&M action is initiated inside an O&Msession, the O&M transaction identifier thus being generated when an O&Maction is initiated.
 25. The telecommunication system according to claim19, wherein the O&M transaction identifier consists of a nodeidentification part comprising an IP-address, or a Fully QualifiedDomain Name, and a running number.
 26. The telecommunication systemaccording to claim 19, wherein the O&M transaction identifier comprisesa node identification part further comprising an IP-address, or a FullyQualified Domain Name; an O&M session identification part comprising arunning sequence number; and an O&M action identification partcomprising a O&M session specific running number.
 27. Thetelecommunication system according to claim 19, wherein thetelecommunication system is a 3GPP based mobile telecommunicationsystem.
 28. The telecommunication system according to claim 27, whereinthe telecommunication system is Wide Code Division Multiple Access(WCDMA).
 29. The telecommunication system according to claim 19, whereinthe telecommunication system is a wired system.
 30. Thetelecommunication system according to claim 19, wherein all O&M actionsare initiated by O&M users, which users are authenticated and authorizedprior to being allowed to perform O&M actions.
 31. The telecommunicationsystem according to claim 19, wherein Integration Reference Point (IRPs)are arranged for handling the communication between the nodes.
 32. Amethod for tracking Operation and Maintenance (O&M) actions in an O&Mhierarchical layer structure, comprising the steps of: performing an O&Maction at a node in the O&M hierarchical layer structure, said O&Maction being initiated inside an O&M session; generating an O&Mtransaction identifier; distributing the action in the form of a commandto at least one other node in the O&M hierarchical layer structure;making the original O&M transaction identifier available as acorresponding O&M transaction identifier at said other node, theoriginal O&M transaction identifier thus being available in all nodes,making it possible to trace the O&M activity throughout the O&Mhierarchical layer structure.
 33. The method according to claim 32,wherein the O&M transaction identifier is generated at any node where anO&M action is initiated and, when needed, said node transfers said O&Mtransaction identifier.
 34. The method according to claim 32, whereinthe O&M transaction identifier is generated when the initiating user isauthenticated.
 35. The method to claim 32, wherein all O&M actions areinitiated by O&M users, which users are authenticated and authorizedprior to being allowed to perform O&M actions.
 36. The method accordingto claim 32, wherein the communication between the nodes usesIntegration Reference Points (IRPs).